Methods and apparatus to obtain transaction confirmation

ABSTRACT

Methods and apparatus to obtain transaction confirmation are described. One example method includes emulating a payment method using a close-proximity communication device of a mobile device, establishing a close-proximity communication link using the close-proximity communication device of the mobile device, transferring payment information from the mobile device using the close-proximity communication device, switching the close-proximity communication device of the mobile device to an information receiving communication mode, and receiving a transaction confirmation at the close-proximity communication device of the mobile device. Other implementations are possible.

FIELD OF THE DISCLOSURE

This disclosure relates generally to wireless transactions and, moreparticularly, to methods and apparatus to obtain transactionconfirmation.

BACKGROUND

Conventionally, wireless payments and transactions result in a separatepaper receipt being generated at a point of sale and the paper receiptbeing handed to the customer. Customers using wireless paymenttechnologies likely have little desire for paper receipts confirmingtheir wireless transactions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example interaction between a mobiledevice and a retailer point of sale.

FIG. 2 is a flow diagram of an example process that may be carried outby the mobile device of FIG. 1 to facilitate a transaction between themobile device and the retailer point of sale in accordance with a firstexample.

FIG. 3 is a flow diagram of an example process that may be carried outby the retailer point of sale of FIG. 1 to facilitate a transactionbetween the mobile device and the retailer point of sale in accordancewith the first example.

FIG. 4 is a flow diagram of an example process that may be carried outby the mobile device of FIG. 1 to facilitate a transaction between themobile device and the retailer point of sale in accordance with a secondexample.

FIG. 5 is a flow diagram of an example process that may be carried outby the retailer point of sale of FIG. 1 to facilitate a transactionbetween the mobile device and the retailer point of sale in accordancewith the second example.

FIG. 6 is a block diagram of an example mobile device in accordance withthe disclosure.

FIG. 7 is a block diagram of example hardware that may be used toimplement the retailer point of sale block diagrams and processesdescribed above.

DETAILED DESCRIPTION

As described below, close-proximity or proximity-based communicationsystems, such as radio frequency identification (RFID), near-fieldcommunication (NFC), and the like, can be used by a mobile device, suchas a smartphone, to interoperate with retail point of sale hardware tofacilitate a transaction between a consumer (or purchaser) and aretailer. That is, upon indicating to the retailer the goods theconsumer desires to purchase, the retailer will inform the consumer ofthe total price of such goods. The consumer may then use his or hermobile device to transfer payment information to the retailer via thepoint of sale hardware using close-proximity communications by movingthe mobile device within range of the point of sale. The retailer maysubsequently verify the validity of the payment information and, if thepayment information is valid, consider the goods paid in full. The pointof sale may then, either automatically or in response to input from theretailer, issue a transaction confirmation, such as a receipt.

An example method described herein includes emulating a payment methodusing a close-proximity communication device of a mobile device,establishing a close-proximity communication link using theclose-proximity communication device of the mobile device, transferringpayment information from the mobile device using the close-proximitycommunication device, switching the close-proximity communication deviceof the mobile device to an information receiving communication mode(e.g., a peer-to-peer mode or a reader/writer mode), and receiving atransaction confirmation at the close-proximity communication device ofthe mobile device.

In an example, the close-proximity communication device of the mobiledevice is controlled to automatically cycle between an emulation modeand the information receiving communication mode. Thus, transferringpayment information and receiving the transaction confirmation arecarried out within a single instance of the close-proximitycommunication device being within range of a point of sale.Alternatively, the switching of the close-proximity communication deviceof the mobile device to the information receiving communication mode maybe carried out after the close-proximity communication device of themobile device is out of range of a point of sale after transferringpayment information from the mobile device using close-proximitycommunication.

An example mobile device may include a close-proximity communicationdevice and a processor coupled to the close-proximity communicationdevice to cause the close-proximity communication device to carry out anumber of tasks. Such tasks may include emulating a payment method,establish a close-proximity communication link with a point of sale,transfer payment information from the mobile device to the point ofsale, switch to an information receiving communication mode, and receivea transaction confirmation from the point of sale.

Also described below is a system that may perform a method includingentering an information receiving communication mode of aclose-proximity communication device at a point of sale, receivingpayment information from a mobile device using the close-proximitycommunication device, switching the close-proximity communication deviceof the point of sale to an emulation mode, and transferring atransaction confirmation to the mobile device. The method may includedetermining whether transfer of transaction confirmation is desired andissuing the transaction confirmation if one is desired. An example pointof sale device or system may include a close-proximity communicationdevice, a processor coupled to the close-proximity communication deviceto cause the close-proximity communication device to perform a number oftasks. The tasks may at least include enter an information receivingcommunication mode of a close-proximity communication device at thepoint of sale, receive payment information from a mobile device usingthe close-proximity communication device, switch the close-proximitycommunication device of the point of sale to an emulation mode, andtransfer a transaction confirmation to the mobile device.

Turning to FIG. 1, a system 100 is shown in which a mobile device 102sends payment information to a point of sale terminal 104, such as aretail point of sale, and receives transaction confirmation information,such as receipt information, from the point of sale terminal 104. Asshown in FIG. 1, the exchange of payment information and receiptinformation between the mobile device 102 and the point of sale terminal104 may be carried out using NFC, in one example. However, any suitableclose-proximity or proximity-based communication technology such as RFIDor the like may be used.

The mobile device 102 may comprise a smartphone, a cellular telephone, atablet computer, a portable computer, a touch pad-based device, or anyother suitable device. A relevant portion of the mobile device 102 isshown in FIG. 1, but the mobile device 102 may include other devices orfunctionality not shown in FIG. 1.

In an example, the mobile device 102 includes a processor or controller110 including instructions stored thereon in a memory 112. The processor110 may be implemented using any suitable microcontroller ormicroprocessor capable of executing instructions. Additionally, theprocessor 102 may include hardware implementations, such asapplication-specific integrated circuits (ASIC), programmable logicdevices (PLDs), or any other suitable logic device or devices. Whileshown as part of the processor 110 in FIG. 1, the memory 112 may beseparate from the processor 110 and may be coupled to the processor 110via one or more conductive lines. The processor 110 is coupled to datanetwork connectivity 114, a secure element 116, and an NFC transceiver118, e.g., a close-proximity communication device. Another example ofthe mobile device 102 is shown in FIG. 6.

The data network connectivity 114 may be implemented using any wirelesscommunication technique. For example, the data network connectivity 114may be hardware or software, or both, that facilitate connection to adigital cellular network. Additionally or alternatively, the datanetwork connectivity 114 may facilitate communication with 802.xx typenetworks or any other suitable data networks. Thus, the data networkconnectivity 114 may provide the cellular and wired fidelity (WIFI) dataconnectivity that is typically found in smartphones.

The secure element 116 stores information related to payment methods, orany other secure information. For example, the secure element 116 maystore information related to credit cards or accounts, debit cards oraccounts, customer loyalty cards or accounts, or any other suitableinformation. The secure element 116 may also store security codes,security keys, or any other suitable information that may be used tofacilitate transactions between the mobile device 102 and the point ofsale terminal 104.

The NFC transceiver 118 is a close-proximity communication device thatmay have many modes and that is controllable by the processor 110. Inone example, the NFC transceiver 118 may enter a transfer mode toemulate a NFC tag containing specified information. The NFC transceiver118 may also operate in an information receiving mode or may operate ina NFC reader/writer mode that is configured to interrogate, sendcommands and information to, and receive information from NFC tags. TheNFC transceiver 118 may be implemented in accordance with theInternational Standards Organization standard ISO 14443. However, othertypes of close-proximity communication devices may be utilized insteadof, or in addition to, the NFC transceiver 118. Additionally, the NFCtransceiver 118 need not be used in favor of utilizing different,independent NFC devices. For example, the NFC transceiver 118 may bereplaced by one or more active or passive NFC tags and an NFCreader/writer, any or all of which may be coupled to the processor 110.

The point of sale terminal 104 may include any number of components suchas cash register, a display screen, etc., but, in the example of FIG. 1,the point of sale terminal 104 includes at least a processor 120 and aNFC transceiver 122.

The processor 120, which is capable of receiving a user input, mayinclude stored instructions in a memory 124, or the instructions may bestored in an alternate memory separate from the processor 120. Theprocessor 120 may be implemented using any suitable microcontroller ormicroprocessor capable of executing instructions. Additionally, theprocessor 120 may include hardware implementations, such as ASICs, PLDs,or any other suitable logic device or devices. The processor 120 may bea stand-alone device, or may be implemented as part of a larger device.For example, in the context of a computer-based cash register, thefunctionality of the processor 120 may be implemented as part of theprocessor performing the cash register functionality. In an example, aportion of the point of sale terminal 104 may be implemented using thehardware of FIG. 7.

The NFC transceiver 122, similar to the NFC transceiver 118 describedabove, may be implemented using a close-proximity communication devicehaving different modes of operation, such as a tag emulation mode, apeer-to-peer mode, and a NFC reader/writer mode. Additionally, the NFCtransceiver 122 may be replaced with one or more NFC tags (passive oractive NFC tags), a NFC reader/writer, or any other suitable components.

As described below in conjunction with processes carried out by themobile device 102 and the point of sale terminal 104, when payment isdue, the point of sale terminal 104 receives payment information fromthe mobile device 102. When the payment information is beingtransferred, the NFC transceiver 118 emulates a NFC tag and the NFCtransceiver 122 operates as a NFC reader/writer. In combination, the NFCtransceiver 118 and the NFC transceiver 122 transfer payment informationfrom the secure element 116 to the point of sale terminal 104 (i.e. thepoint of sale terminal 104 may read the payment information from themobile device 102). After the payment information has been received, theNFC transceiver 122 enters a transfer mode and emulates a NFC tag havingtransaction confirmation information stored therein and the NFCcontroller 118 operates as a NFC reader/writer to obtain the transactionconfirmation information (i.e. the mobile device 102 may read thetransaction confirmation information from the point of sale 104).Alternatively, the NFC transceiver 122 may enter a peer-to-peer mode.

Flowcharts representative of example processes that may be executed toimplement some or all of the elements and devices described herein aredescribed below and shown in the drawings. In these examples, theprocess represented by each flowchart may be implemented by one or moreprograms comprising machine readable instructions for execution by aprocessor or controller or any suitable hardware, such as shown in FIG.1, FIG. 6, FIG. 7, or any other suitable device.

The one or more programs may be embodied in software or softwareinstructions stored on a tangible medium such as, for example, a flashmemory, a CD-ROM, a hard drive, a DVD, or a memory associated with aprocessor, but the entire program or programs and/or portions thereofcould alternatively be executed by a device other than themicroprocessor and/or embodied in firmware or dedicated hardware (e.g.,implemented by an application specific integrated circuit (ASIC), aprogrammable logic device (PLD), a field programmable logic device(FPLD), discrete logic, etc.). For example, any one, some or all of theexample mobile communications system components could be implemented byany combination of software, hardware, and/or firmware. Also, some orall of the processes represented by the flowcharts may be implementedmanually. As used herein, the term tangible computer readable medium isexpressly defined to include any type of computer readable storage.

Additionally or alternatively, the example processes described hereinmay be implemented using coded instructions (e.g., computer readableinstructions) stored on a non-transitory computer readable medium suchas a hard disk drive, a flash memory, a read-only memory, a compactdisk, a digital versatile disk, a cache, a random-access memory and/orany other storage media in which information is stored for any duration(e.g., for extended time periods, permanently, brief instances, fortemporarily buffering, and/or for caching of the information). As usedherein, the term non-transitory computer readable medium is expresslydefined to include any type of computer readable medium.

The processes of FIGS. 2 and 3 operate together, one on the mobiledevice 102 and one on the retail point of sale (POS) 104, to facilitatea payment and transaction confirmation information exchange within asingle instance of the close-proximity communication device (e.g., theNFC transceiver 118) of the mobile device 102 being within range of theretail point of sale NFC transceiver 122.

A process 200, as shown in FIG. 2, may be carried out by a mobiledevice, such as the mobile device 102 of FIG. 1. For example,instructions implementing some or all of the process 200 of FIG. 2 maybe stored in the memory 112 and executed by the processor 110. Themobile device 102 enters mode cycling wherein the processor 110 and theNFC transceiver 118 cooperate to cause the mode of the NFC transceiverto cycle between (1) an emulation mode during which the NFC transceiver118 emulates a payment method or a peer-to-peer mode and (2) aninformation receiving communication mode, such as a NFC read/write modeor a peer-to-peer mode during which information can be read by the NFCtransceiver 118 (block 202). During the mode cycling, the NFCtransceiver 118 may automatically cycle between the emulation andinformation receiving communication modes. The mobile device 102 waitsuntil it is in proximity of the point of sale terminal 104 (block 204)and, when the mobile device 102 is within proximity of the point of saleterminal 104, payment is made by the NFC transceiver 118 operating inemulation mode (block 206). The payment may be made in response to aread/write signal or any suitable interrogation signal transmitted fromthe NFC transceiver 122 (the corresponding operation of which isdescribed below). Because the NFC transceiver 118 is still mode cyclingbetween emulation and information receiving communication modes, the NFCtransceiver 118, while the mobile device 102 is still proximate thepoint of sale terminal 104 after payment (block 206), will transitioninto an information receiving communication mode, such as areader/writer mode, at which time the NFC transceiver 118 will receivethe transaction confirmation information, which may take the form of areceipt (block 208). After the transaction confirmation information isreceived, it may be displayed to the user on the mobile device 102display screen or stored in the mobile device 102, or both.

Operation of the point of sale terminal 104 corresponding to theoperation of the mobile device 102 described above is shown in FIG. 3 asa process 300. Instructions implementing some or all of the process 300of FIG. 3 may be stored in the memory 124 and executed by the processor120. The processor 120 and the NFC transceiver 122 cooperate to put theNFC transceiver 122 in reader/writer mode (block 302). In thereader/writer mode, the NFC transceiver 122 is capable of readinginformation from NFC tags or from NFC transceivers (e.g., the NFCtransceiver 118) that are emulating NFC tags. When the NFC transceiver118 of the mobile device 102 is in proximity of the point of saleterminal 104 (block 304), the NFC transceiver 122 reads the NFCtransceiver 118, which is emulating a NFC tag with payment informationand payment is received (block 306).

After the payment is received (block 306), the NFC transceiver 122enters a transfer mode to transfers the transaction confirmation (block308). For example, when entering the transfer mode the NFC transceiver122 may emulate a NFC tag having the transaction confirmationinformation stored thereon such that when the NFC transceiver 118 cyclesinto the information receiving communication mode (block 208, above),the NFC transceiver 118 reads the NFC transceiver 122. In anotherexample, the NFC transceiver 122 may enter a peer-to-peer mode totransfer the transaction confirmation information. When the transactionconfirmation has been transferred (block 310) or a timeout has occurred(block 312), the NFC transceiver 122 returns to the reader/writer modeto await the next payment transaction (block 302). If the transactionconfirmation has not been transferred (block 310) and a timeout has notoccurred (block 312), the NFC transceiver 122 may remain in emulationmode, ready to transfer the transaction confirmation (block 308).

The processes of FIGS. 4 and 5 operate together, one on the mobiledevice 102 and one on the retail point of sale (POS) 104, to facilitatea payment and transaction confirmation information exchange, whereinafter payment the mobile device 102 is removed from proximity of thepoint of sale terminal 104 before it is again placed within proximity ofthe point of sale terminal 104 to receive the transaction confirmationinformation. Thus, the mobile device 102 is brought in proximity of thepoint of sale terminal 104 two times, once to make payment and once toreceive the transaction confirmation information.

According to the process 400 of FIG. 4, the mobile device 102 enters anemulation mode (block 402) during which the NFC transceiver 118 cantransfer payment information from the secure element 116. In analternative, the mobile device 102 may enter a peer-to-peer mode. Whenthe mobile device 102 and, more particularly, the NFC transceiver 118,are in proximity to the point of sale terminal 104 (block 404), paymentis made by transferring information from the secure element 116 via theNFC transceiver 118 to the NFC transceiver 122 (block 406).

The user may then move the mobile device 102 out of proximity of thepoint of sale terminal 104 (block 408), at which point the NFCtransceiver 118 of the mobile device 102 enters an information receivingcommunication mode, such as a reader/writer mode or a peer-to-peer mode(block 410). After the mobile device 102 is in proximity of the point ofsale terminal 104 (block 412), the transaction confirmation informationmay be received (block 414). The received transaction confirmationinformation may be displayed and stored (blocks 416). In one example,the received transaction confirmation may be stored at one point in timeand displayed at a later point in time at user direction. Alternatively,if the transaction confirmation information is not received, a timeoutmay occur (block 418). If the transaction confirmation is received anddisplayed or stored (block 416) or a timeout occurs (block 418), the NFCtransceiver 118 of the mobile device 102 returns to emulation mode(block 402). Instructions implementing some or all of the process 400 ofFIG. 4 may be stored in the memory 112 and executed by the processor110.

Operation of the point of sale terminal 104 corresponding to theoperation of the mobile device 102 described above in conjunction withFIG. 4 is shown in FIG. 5 as a process 500. Instructions implementingsome or all of the process 500 of FIG. 5 may be stored in the memory 124and executed by the processor 120. The processor 120 and the NFCtransceiver 122 cooperate to put the NFC transceiver 122 inreader/writer mode (block 502). In the reader/writer mode, the NFCtransceiver 122 is capable of reading information from NFC tags or fromNFC transceivers (e.g., the NFC transceiver 118) that are emulating NFCtags. When the NFC transceiver 118 of the mobile device 102 is inproximity of the point of sale terminal 104 (block 504), the NFCtransceiver 122 reads the NFC transceiver 118, which is emulating a NFCtag with payment information and payment is received (block 506).

After the payment is received (block 506), the process point of saleterminal 104 determines whether a transaction confirmation (e.g. areceipt) is requested (block 508). The determination of whether atransaction confirmation is requested may be made by user input to theprocessor 120 of the point of sale terminal 104, or an indication may bereceived from the mobile device 102. For example, user input may includea merchant selecting a key that informs the point of sale terminal 104that a transaction confirmation is requested or desired by the customer.If no transaction confirmation is requested (block 508), the retailpoint of sale remains in the reader/writer mode (block 502).

If a transaction confirmation is requested (block 508), the NFCtransceiver 122 enters a transfer mode and emulates the transactionconfirmation (block 510). For example, the NFC transceiver 122 mayemulate a NFC tag having the transaction confirmation information storedthereon such that when the NFC transceiver 118 enters into theinformation receiving communication mode (block 410, above), the NFCtransceiver 118 reads the NFC transceiver 122. In another example, theNFC transceiver 122 may enter a peer-to-peer mode to send thetransaction confirmation information. When the transaction confirmationhas been transferred (block 512) or a timeout has occurred (block 514),the NFC transceiver 122 returns to the reader/writer mode to await thenext payment transaction (block 302). If the transaction confirmationhas not been transferred (block 512) and a timeout has not occurred(block 514), the NFC transceiver 122 remains in emulation mode, ready totransfer the transaction confirmation (block 510).

A block diagram of an example mobile device 102, which may be carry outthe processes of FIG. 2 and/or FIG. 4, is shown in FIG. 6. The mobiledevice 102 includes multiple components, such as a processor 602 thatcontrols the overall operation of the mobile device 102. Communicationfunctions, including data and voice communications, are performedthrough a communication subsystem 604. Data received by the mobiledevice 102 is decompressed and decrypted by a decoder 606. Thecommunication subsystem 604 receives messages from and sends messages toa wireless network 646. The wireless network 646 may be any type ofwireless network, including, but not limited to, data wireless networks,voice wireless networks, and networks that support both voice and datacommunications. A power source 652, such as one or more rechargeablebatteries or a port to an external power supply, powers the mobiledevice 102.

The processor 602 interacts with other components, such as Random AccessMemory (RAM) 608, memory 610, a display 612 with a touch-sensitiveoverlay 614 operably connected to an electronic controller 616 thattogether comprise a touch-sensitive display 618, one or more actuatorapparatus 620, one or more force sensors 622, a keypad 624, an auxiliaryinput/output (I/O) subsystem 626, a data port 628, a speaker 630, amicrophone 632, short-range communications 638, and other devicesubsystems 640. User-interaction with a graphical user interface isperformed through the touch-sensitive display 618. The processor 602interacts with the touch-sensitive overlay 614 via the electroniccontroller 616. Information, such as text, characters, symbols, images,icons, and other items that may be displayed or rendered on the mobiledevice 102, is displayed on the touch-sensitive display 618 via theprocessor 602. In some examples, the display 612 may include a primarydisplay and a secondary display.

To identify a subscriber for network access, the mobile device 102 usesa Subscriber Identity Module or a Removable User Identity Module(SIM/RUIM) card 644 for communication with a network, such as thewireless network 646. Alternatively, user identification information maybe programmed into memory 610.

The mobile device 102 includes an operating system 648 and softwareprograms or components 650 that are executed by the processor 602 toimplement various applications and instructions to carry out processesdescribed herein and are typically stored in a persistent, updatablestore such as the memory 610. Additional applications or programs may beloaded onto the portable electronic device 102 through the wirelessnetwork 646, the auxiliary I/O subsystem 626, the data port 628, theshort-range communications subsystem 638, or any other suitablesubsystem 640.

A received signal such as a text message, an e-mail message, or web pagedownload is processed by the communication subsystem 604 and input tothe processor 602. The processor 602 processes the received signal foroutput to the display 612 and/or to the auxiliary I/O subsystem 626. Asubscriber may generate data items, for example e-mail messages, whichmay be transmitted over the wireless network 646 through thecommunication subsystem 604. For voice communications, the overalloperation of the mobile device 102 is similar. The speaker 630 outputsaudible information converted from electrical signals, and themicrophone 632 converts audible information into electrical signals forprocessing.

The short-range communications 638 functionality may be NFC, RFID, orany other suitable short-range or close-proximity communicationtechnology. As described herein, the short-range communications 638 maybe used to facilitate transactions with a retail point of sale.

FIG. 7 is a block diagram of an example processing system 700 capable ofimplementing the apparatus and methods disclosed herein. The processingsystem 700 can correspond to, for example, a mobile device, a retailpoint of sale, or any other type of computing device.

The system 700 of the instant example includes a processor 712 such as ageneral purpose programmable processor, an embedded processor, amicrocontroller, etc. The processor 712 includes a local memory 714, andexecutes coded instructions present in the local memory 714 and/or inanother memory device. The processor 712 may execute, among otherthings, machine readable instructions to implement any, some or all ofthe processes represented in FIGS. 3 and 5. The processor 712 may be anytype of processing unit, such as one or more microprocessors, one ormore microcontrollers, etc. Of course, other processors are alsoappropriate.

The processor 712 is in communication with a main memory including avolatile memory 718 and a non-volatile memory 720 via a bus 722. Thevolatile memory 718 may be implemented by Static Random Access Memory(SRAM), Synchronous Dynamic Random Access Memory (SDRAM), Dynamic RandomAccess Memory (DRAM), RAIVIBUS Dynamic Random Access Memory (RDRAM)and/or any other type of random access memory device. The non-volatilememory 720 may be implemented by flash memory and/or any other desiredtype of memory device. Access to the main memory 718, 720 is typicallycontrolled by a memory controller (not shown).

The system 700 also includes an interface circuit 724. The interfacecircuit 724 may be implemented by any type of interface standard, suchas an Ethernet interface, a universal serial bus (USB), and/or a thirdgeneration input/output (3GIO) interface.

One or more input devices 726 are connected to the interface circuit724. The input device(s) 726 permit a user to enter data and commandsinto the processor 712. The input device(s) can be implemented by, forexample, a keyboard, a mouse, a touchscreen, a track-pad, a trackball,an isopoint and/or a voice recognition system.

One or more output devices 728 are also connected to the interfacecircuit 724. The output devices 728 can be implemented, for example, bydisplay devices (e.g., a liquid crystal display), by a printer and/or byspeakers. The interface circuit 724, thus, typically includes a graphicsdriver card.

The interface circuit 724 also includes a communication device such as amodem or network interface card to facilitate exchange of data withexternal computers via a network (e.g., an Ethernet connection, adigital subscriber line (DSL), a telephone line, coaxial cable, acellular telephone system such as an EGPRS-compliant system, etc.).

The system 700 also includes one or more mass storage devices 730 forstoring software and data. Examples of such mass storage devices 730include hard drive disks, compact disk drives and digital versatile disk(DVD) drives.

As an alternative to implementing the methods and/or apparatus describedherein in a system such as shown in FIG. 7, the methods and or apparatusdescribed herein may be embedded in a structure such as a processorand/or an ASIC (application specific integrated circuit).

Further, although the example processes are described with reference toflowcharts, many other techniques for implementing the example methodsand apparatus described herein may alternatively be used. For example,with reference to the flowcharts, the order of execution of the blocksmay be changed, and/or some of the blocks described may be changed,eliminated, combined, and/or subdivided into multiple blocks. Any of thedescribed blocks may be as implemented as part of an existing system.While the example block diagrams are described as implementing theprocesses of the flowcharts, the apparatus of the block diagrams mayimplement any process and, likewise, the processes of the flowcharts maybe implemented by any apparatus, device, system, software, orcombination thereof.

Finally, although certain example methods, apparatus and articles ofmanufacture have been described herein, the scope of coverage of thisdisclosure is not limited thereto. On the contrary, this disclosurecovers all methods, apparatus and articles of manufacture andequivalents described and claimed herein.

1-25. (canceled)
 26. A method of a mobile device comprising:establishing a close-proximity communication link to a point of saleterminal using a close-proximity communication device of the mobiledevice, wherein the close-proximity communication device includes anear-field communication (NFC) transceiver; emulating a payment methodusing the NFC transceiver of the close-proximity communication device;transferring, in an emulation mode of the NFC transceiver of theclose-proximity communication device, payment information from themobile device to the point of sale terminal; and receiving, in aninformation receiving communication mode of the NFC transceiver of theclose-proximity communication device, a transaction confirmation fromthe point of sale terminal, wherein the NFC transceiver of theclose-proximity communication device switches from the emulation modeand to the information receiving communication mode.
 27. The method ofclaim 26, wherein the transferring of the payment information and thereceiving of the transaction confirmation are carried out within asingle instance of the mobile device being in close-proximity of thepoint of sale terminal.
 28. The method of claim 27, wherein the NFCtransceiver automatically cycles between the emulation mode and theinformation receiving communication mode during the single instance ofthe close-proximity communication device of the mobile device beingwithin range of the close-proximity communication device of the point ofsale terminal.
 29. The method of claim 28, wherein the close-proximitycommunication link is established when the close-proximity communicationdevice is in the emulation mode.
 30. The method of claim 26, wherein theinformation receiving communication mode comprises a peer-to-peercommunication mode.
 31. The method of claim 26, wherein theclose-proximity communication link comprises a near-field communication(NFC) link.
 32. The method of claim 26, wherein the transactionconfirmation comprises a receipt.
 33. The method of claim 32, whereinthe transaction confirmation further comprises displaying the receipt onthe mobile device.
 34. The method of claim 26, wherein the paymentmethod comprises a credit card payment method.
 35. A mobile devicecomprising: a close-proximity communication device, wherein theclose-proximity communication device includes a near-field communication(NFC) transceiver; and a processor coupled with the close-proximitycommunication device, the processor being configured to cause theclose-proximity communication device to: establish a close-proximitycommunication link to a point of sale terminal using a close-proximitycommunication device of the mobile device, wherein the close-proximitycommunication device includes a near-field communication (NFC)transceiver; emulate a payment method using the NFC transceiver of theclose-proximity communication device; transfer, in an emulation mode ofthe NFC transceiver of the close-proximity communication device, paymentinformation from the mobile device to the point of sale terminal; andreceive, in an information receiving communication mode of the NFCtransceiver of the close-proximity communication device, a transactionconfirmation from the point of sale terminal, wherein the NFCtransceiver of the close-proximity communication device switches fromthe emulation mode and to the information receiving communication mode.36. The mobile device of claim 35, wherein the transferring of thepayment information and the receiving of the transaction confirmationare carried out within a single instance of the mobile device being inclose-proximity of the point of sale terminal.
 37. The mobile device ofclaim 36, wherein the NFC transceiver automatically cycles between theemulation mode and the information receiving communication mode duringthe single instance of the close-proximity communication device of themobile device being within range of the close-proximity communicationdevice of the point of sale terminal.
 38. The mobile device of claim 35,wherein the information receiving communication mode comprises apeer-to-peer communication mode.
 39. The mobile device of claim 35,wherein the close-proximity communication link comprises a near-fieldcommunication (NFC) link.
 40. The mobile device of claim 35, wherein thetransaction confirmation comprises a receipt.
 41. The mobile device ofclaim 35, further comprising a display coupled with the processor,wherein the processor is further configured to cause the receipt to bepresented on the display of the mobile device.
 42. A tangible,non-transitory computer-readable medium encoded with computer-executableinstructions, wherein execution of the computer-executable instructionsis for: establishing a close-proximity communication link to a point ofsale terminal using a close-proximity communication device of the mobiledevice, wherein the close-proximity communication device includes anear-field communication (NFC) transceiver; emulating a payment methodusing the NFC transceiver of the close-proximity communication device;transferring, in an emulation mode of the NFC transceiver of theclose-proximity communication device, payment information from themobile device to the point of sale terminal; and receiving, in aninformation receiving communication mode of the NFC transceiver of theclose-proximity communication device, a transaction confirmation fromthe point of sale terminal, wherein the NFC transceiver of theclose-proximity communication device switches from the emulation modeand to the information receiving communication mode.
 43. The tangible,non-transitory computer readable medium of claim 42, wherein thetransferring of the payment information and the receiving of thetransaction confirmation are carried out within a single instance of themobile device being in close-proximity of the point of sale terminal.44. The tangible, non-transitory computer readable medium of claim 43,wherein the NFC transceiver automatically cycles between the emulationmode and the information receiving communication mode during the singleinstance of the close-proximity communication device of the mobiledevice being within range of the close-proximity communication device ofthe point of sale terminal.
 45. The tangible, non-transitory computerreadable medium of claim 42, wherein the close-proximity communicationlink is established when the close-proximity communication device is inthe emulation mode.